-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: make test-crypto-hash compatible with OpenSSL > 3.4.0 #56160
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #56160 +/- ##
==========================================
- Coverage 89.18% 89.17% -0.01%
==========================================
Files 662 662
Lines 191751 191759 +8
Branches 36909 36908 -1
==========================================
- Hits 171008 171001 -7
- Misses 13604 13613 +9
- Partials 7139 7145 +6 |
test/common/index.js
Outdated
get hasOpenSSL34() { | ||
return hasOpenSSL(3, 4); | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I added hasOpenSSL()
in #53456, the idea was to stop adding new functions for every OpenSSL version to common
, and instead directly call, e.g.hasOpenSSL(3, 4)
in the test.
Can you please rebase to fix the conflict and address Richard's review? Let me know if you'd prefer me to do it instead |
93eabf6
to
4f8bc73
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as duplicate.
This comment was marked as duplicate.
Now that the holidays are over, done :) |
OpenSSL 3.4 has a breaking change where the outputLength is now mandatory for shake* hash algorithms. openssl/openssl@b911fef
This comment was marked as outdated.
This comment was marked as outdated.
The shake128/shake256 hashing algorithms broke due to an OpenSSL 3.4 incompatible change and now throws an Error.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 496e17e...e6a988d |
OpenSSL 3.4 has a breaking change where the outputLength is now mandatory for shake* hash algorithms. openssl/openssl@b911fef PR-URL: #56160 Refs: #56159 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
The shake128/shake256 hashing algorithms broke due to an OpenSSL 3.4 incompatible change and now throws an Error. PR-URL: #56160 Refs: #56159 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
OpenSSL 3.4 has a breaking change where the outputLength is now mandatory for shake* hash algorithms. openssl/openssl@b911fef PR-URL: nodejs#56160 Refs: nodejs#56159 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
The shake128/shake256 hashing algorithms broke due to an OpenSSL 3.4 incompatible change and now throws an Error. PR-URL: nodejs#56160 Refs: nodejs#56159 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
OpenSSL 3.4 has a breaking change where the outputLength is now mandatory for shake* hash algorithms.
openssl/openssl@b911fef
This only fixes one of the tree issues with OpenSSL 3.4. and it doesn't fix
crypto.createHash()
which likely should be adjusted to be compatible with the new OpenSSL behaviour but I am unsure how that is done. I assume it should raise an InvalidArgumentError now.Refs: #56159